Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 707e3f496b7f958bb17ac9f950b13c5c800455d64996d8c161614d0d42504162

Tx prefix hash: a99a37628cc3a8c7f5747bc2cb983d98f1e96109b08f3d834c271a0ab5cb29af
Tx public key: 3e85e85827ba853d81aae8cfb1daf69b05d830fbb9f1a99e6940e9590027dfc1
Timestamp: 1626014120 Timestamp [UCT]: 2021-07-11 14:35:20 Age [y:d:h:m:s]: 04:135:11:57:55
Block: 291913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126181 RingCT/type: yes/0
Extra: 013e85e85827ba853d81aae8cfb1daf69b05d830fbb9f1a99e6940e9590027dfc102110000003dd2fc4d28000000000000000000

1 output(s) for total of 66.189065934000 dcy

stealth address amount amount idx
00: bbd76891b6551d299279793bb2377171973b0dcd92f40c6915cfff3514b6abf6 66.189065934000 611679 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": 291923, "vin": [ { "gen": { "height": 291913 } } ], "vout": [ { "amount": 66189065934, "target": { "key": "bbd76891b6551d299279793bb2377171973b0dcd92f40c6915cfff3514b6abf6" } } ], "extra": [ 1, 62, 133, 232, 88, 39, 186, 133, 61, 129, 170, 232, 207, 177, 218, 246, 155, 5, 216, 48, 251, 185, 241, 169, 158, 105, 64, 233, 89, 0, 39, 223, 193, 2, 17, 0, 0, 0, 61, 210, 252, 77, 40, 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