Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb06e014279f680b47411d37dec9e38786b84f57563b43927d470a5cb280173f

Tx prefix hash: 5589f251672c3ccde08ba056429142a0ac9eac0828e8dba5f869325634ed2c33
Tx public key: 767504ab845eaac035c0e96e6a5d0106d9fd0d0976581d63783b00e322d407b5
Timestamp: 1741278589 Timestamp [UCT]: 2025-03-06 16:29:49 Age [y:d:h:m:s]: 00:007:06:51:24
Block: 1233505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5225 RingCT/type: yes/0
Extra: 01767504ab845eaac035c0e96e6a5d0106d9fd0d0976581d63783b00e322d407b5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b5a328a422681d86e000f62a0e68f25642a482f2a22c416aa82e025b5e0363a 0.600000000000 1720426 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": 1233515, "vin": [ { "gen": { "height": 1233505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b5a328a422681d86e000f62a0e68f25642a482f2a22c416aa82e025b5e0363a" } } ], "extra": [ 1, 118, 117, 4, 171, 132, 94, 170, 192, 53, 192, 233, 110, 106, 93, 1, 6, 217, 253, 13, 9, 118, 88, 29, 99, 120, 59, 0, 227, 34, 212, 7, 181, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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