Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f20a5b01f0a9cd63aa87d7cf66a39f568281b67562b9806c331852b066916faa

Tx prefix hash: 91efaeef57a242e34e906e650399b259d2f33db5b029a6de3cf08661458b8062
Tx public key: d654ae35d6a2adf564266f978abc815b0bdd78138642555008dbeb153da94892
Timestamp: 1712250284 Timestamp [UCT]: 2024-04-04 17:04:44 Age [y:d:h:m:s]: 00:326:13:02:37
Block: 993275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233462 RingCT/type: yes/0
Extra: 01d654ae35d6a2adf564266f978abc815b0bdd78138642555008dbeb153da948920211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc222c0baee4a0d397e93c1557e6e79ddf4cc482d4cb4ad35ce544a9c1d082bc 0.600000000000 1453661 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 993285, "vin": [ { "gen": { "height": 993275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc222c0baee4a0d397e93c1557e6e79ddf4cc482d4cb4ad35ce544a9c1d082bc" } } ], "extra": [ 1, 214, 84, 174, 53, 214, 162, 173, 245, 100, 38, 111, 151, 138, 188, 129, 91, 11, 221, 120, 19, 134, 66, 85, 80, 8, 219, 235, 21, 61, 169, 72, 146, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8