Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 299403a8dfd348e2c946bec94129c04d357b1ba46b72f6423020c08fb576dd5c

Tx prefix hash: 7f47a3df5249765cf70870810187e860f3ef73c6bcfa3f08d2930c7535c710b3
Tx public key: d0e2c79d2828ac6e0dc4dc08443361ee1c40d1ec1304c757389e4615b3aaf2e3
Timestamp: 1711016492 Timestamp [UCT]: 2024-03-21 10:21:32 Age [y:d:h:m:s]: 00:364:00:21:11
Block: 983101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260270 RingCT/type: yes/0
Extra: 01d0e2c79d2828ac6e0dc4dc08443361ee1c40d1ec1304c757389e4615b3aaf2e30211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bef514407cefb12ac7047b49e5e453e78217bd506e2cd0991d102d3bdfb1e190 0.600000000000 1443222 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": 983111, "vin": [ { "gen": { "height": 983101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bef514407cefb12ac7047b49e5e453e78217bd506e2cd0991d102d3bdfb1e190" } } ], "extra": [ 1, 208, 226, 199, 157, 40, 40, 172, 110, 13, 196, 220, 8, 68, 51, 97, 238, 28, 64, 209, 236, 19, 4, 199, 87, 56, 158, 70, 21, 179, 170, 242, 227, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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