Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdd7593aadcafb4065db05854faa4143d525d52b1e528594f542610fa7acb1a2

Tx prefix hash: 8a0f44ec34e6e180a259f41b127276b95c689fcc15b1663aa77c32dc5f8b07e4
Tx public key: 3706e7f1c7cb63ee4f3621f62d4b67b9873b256bf5d3edb419b17056cdb68866
Timestamp: 1713545376 Timestamp [UCT]: 2024-04-19 16:49:36 Age [y:d:h:m:s]: 00:363:21:57:54
Block: 1004035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260177 RingCT/type: yes/0
Extra: 013706e7f1c7cb63ee4f3621f62d4b67b9873b256bf5d3edb419b17056cdb6886602110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ded276111722d5e58470ce5acef2dd371cf0ac924d29d568414bed8c3206be3d 0.600000000000 1464597 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": 1004045, "vin": [ { "gen": { "height": 1004035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ded276111722d5e58470ce5acef2dd371cf0ac924d29d568414bed8c3206be3d" } } ], "extra": [ 1, 55, 6, 231, 241, 199, 203, 99, 238, 79, 54, 33, 246, 45, 75, 103, 185, 135, 59, 37, 107, 245, 211, 237, 180, 25, 177, 112, 86, 205, 182, 136, 102, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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