Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb303399e51154f68ab5018100d3f3374c083f67d79314e7269d0c4f9c98294

Tx prefix hash: 7c09ad2ba5456a1e0eecbfe27349f3211bd7667b26ed2fa67f066596c56aa2a7
Tx public key: 2585929bc84111afefdabf4c0a3a71cc5b38f7e919926f637044a202092e078a
Timestamp: 1733724932 Timestamp [UCT]: 2024-12-09 06:15:32 Age [y:d:h:m:s]: 00:140:14:19:25
Block: 1171241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100304 RingCT/type: yes/0
Extra: 012585929bc84111afefdabf4c0a3a71cc5b38f7e919926f637044a202092e078a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4a9bca9d1a95fca4e9c2c1344e3a54c015c3fee95f4c7c810cee07733a64680 0.600000000000 1656980 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": 1171251, "vin": [ { "gen": { "height": 1171241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4a9bca9d1a95fca4e9c2c1344e3a54c015c3fee95f4c7c810cee07733a64680" } } ], "extra": [ 1, 37, 133, 146, 155, 200, 65, 17, 175, 239, 218, 191, 76, 10, 58, 113, 204, 91, 56, 247, 233, 25, 146, 111, 99, 112, 68, 162, 2, 9, 46, 7, 138, 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