Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 338f9e7efe49ca2489c3d0e2736873a262224dcfba6c6350d9776ce3a9988d60

Tx prefix hash: 22484d3dc613e75cf05dd0c682a89891a2ca88aa6a04d1510fb2b41cb18035b0
Tx public key: a6e3ba9934428367c41648fe766d53100528949ca4afd3a03a5d85f28b8427bb
Timestamp: 1717888879 Timestamp [UCT]: 2024-06-08 23:21:19 Age [y:d:h:m:s]: 00:350:20:08:43
Block: 1040056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250766 RingCT/type: yes/0
Extra: 01a6e3ba9934428367c41648fe766d53100528949ca4afd3a03a5d85f28b8427bb0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e137f3e6212c2a5b17f72e2bbe93a782e308da6ec04c62e4b2841a80561e7a1a 0.600000000000 1508711 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": 1040066, "vin": [ { "gen": { "height": 1040056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e137f3e6212c2a5b17f72e2bbe93a782e308da6ec04c62e4b2841a80561e7a1a" } } ], "extra": [ 1, 166, 227, 186, 153, 52, 66, 131, 103, 196, 22, 72, 254, 118, 109, 83, 16, 5, 40, 148, 156, 164, 175, 211, 160, 58, 93, 133, 242, 139, 132, 39, 187, 2, 17, 0, 0, 0, 8, 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