Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bf7f50b3f11bf5ccbbdb1e551558452ab436e2b8ed690f17426319b864c879b

Tx prefix hash: 65f3df66b365a755095e66462b6b66b5cb1ca20041c979e8d8ac4245eb90708f
Tx public key: 1a09493fcd962920c0603ee83849a23bc9102c6f0d63bacd0ed418d245d5a549
Timestamp: 1704153924 Timestamp [UCT]: 2024-01-02 00:05:24 Age [y:d:h:m:s]: 01:165:18:27:53
Block: 926171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379538 RingCT/type: yes/0
Extra: 011a09493fcd962920c0603ee83849a23bc9102c6f0d63bacd0ed418d245d5a549021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30a927a851cc64c3ee7953d57ea8b13927c3a8c2c3dfb84a4019cf0a23fe268e 0.600000000000 1383945 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": 926181, "vin": [ { "gen": { "height": 926171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30a927a851cc64c3ee7953d57ea8b13927c3a8c2c3dfb84a4019cf0a23fe268e" } } ], "extra": [ 1, 26, 9, 73, 63, 205, 150, 41, 32, 192, 96, 62, 232, 56, 73, 162, 59, 201, 16, 44, 111, 13, 99, 186, 205, 14, 212, 24, 210, 69, 213, 165, 73, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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