Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2d1556b299e2ea547bad98f89f3ff85717a733dbabcc1574d9a5d24ed1046c7

Tx prefix hash: 409ad3b5fcc5a041c75439dab2de977c801e77a60df4894d31b91b3e93ffa653
Tx public key: 72f8142080d27ccbaaa62a0fdf04dde3afeed4ba61604a57a0f813a2eea82d73
Timestamp: 1626726649 Timestamp [UCT]: 2021-07-19 20:30:49 Age [y:d:h:m:s]: 03:258:22:03:25
Block: 297134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 956445 RingCT/type: yes/0
Extra: 0172f8142080d27ccbaaa62a0fdf04dde3afeed4ba61604a57a0f813a2eea82d730211000000242a81b072000000000000000000

1 output(s) for total of 63.603310009000 dcy

stealth address amount amount idx
00: d2d33b6c10a109ab9946306cbf3baa7dc076808e62a8ac3e931d5659810de592 63.603310009000 621964 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": 297144, "vin": [ { "gen": { "height": 297134 } } ], "vout": [ { "amount": 63603310009, "target": { "key": "d2d33b6c10a109ab9946306cbf3baa7dc076808e62a8ac3e931d5659810de592" } } ], "extra": [ 1, 114, 248, 20, 32, 128, 210, 124, 203, 170, 166, 42, 15, 223, 4, 221, 227, 175, 238, 212, 186, 97, 96, 74, 87, 160, 248, 19, 162, 238, 168, 45, 115, 2, 17, 0, 0, 0, 36, 42, 129, 176, 114, 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