Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b632ef494fcfab94e1321076ef5ee25df06aa3c084eb7a813f500a7bae8d4399

Tx prefix hash: ff2d6e3e116e2d0c23da351f1ff9afbd8785bd2d92eeefcc91917593b2d50d62
Tx public key: eb54bbb5f8ed7b297c37a9d19da37399f61f9025036f93d4fdce88fc95e51630
Timestamp: 1727480266 Timestamp [UCT]: 2024-09-27 23:37:46 Age [y:d:h:m:s]: 01:040:00:40:12
Block: 1119566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286991 RingCT/type: yes/0
Extra: 01eb54bbb5f8ed7b297c37a9d19da37399f61f9025036f93d4fdce88fc95e5163002110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3e3d0e30f77317a1e2b848939014ca47920ed0bc1beca0027dd360ad077c956 0.600000000000 1601169 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": 1119576, "vin": [ { "gen": { "height": 1119566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3e3d0e30f77317a1e2b848939014ca47920ed0bc1beca0027dd360ad077c956" } } ], "extra": [ 1, 235, 84, 187, 181, 248, 237, 123, 41, 124, 55, 169, 209, 157, 163, 115, 153, 246, 31, 144, 37, 3, 111, 147, 212, 253, 206, 136, 252, 149, 229, 22, 48, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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