Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2a006155204526c5d7700102f14c8a171e151c157f910d2d254ca8cb5cd0737

Tx prefix hash: a9129fdeb700b35f2379c65481b5d7bd3d91d5aa8719f29d8276bd9eb403ce8e
Tx public key: 651234cb1550224319ca6f0e09fc11847ca528b827b7aaaa0dceebe380eaa97a
Timestamp: 1577554806 Timestamp [UCT]: 2019-12-28 17:40:06 Age [y:d:h:m:s]: 05:156:04:55:00
Block: 33660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1261548 RingCT/type: yes/0
Extra: 01651234cb1550224319ca6f0e09fc11847ca528b827b7aaaa0dceebe380eaa97a0211000000029159db1e000000000000000000

1 output(s) for total of 474.756920341000 dcy

stealth address amount amount idx
00: 4cd8358267f71cc58eea46f0ba399cd587342c2b8a2bbd6ba8a3a8f4f9826e1e 474.756920341000 56451 of 0

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": 33670, "vin": [ { "gen": { "height": 33660 } } ], "vout": [ { "amount": 474756920341, "target": { "key": "4cd8358267f71cc58eea46f0ba399cd587342c2b8a2bbd6ba8a3a8f4f9826e1e" } } ], "extra": [ 1, 101, 18, 52, 203, 21, 80, 34, 67, 25, 202, 111, 14, 9, 252, 17, 132, 124, 165, 40, 184, 39, 183, 170, 170, 13, 206, 235, 227, 128, 234, 169, 122, 2, 17, 0, 0, 0, 2, 145, 89, 219, 30, 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