Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b9d404e538b5c714ba7c60f19cfb8d3dc564ffb94c1015c940ed8d9c3f93e7c

Tx prefix hash: 725652fae52ea30e764483a503fe07d09b1f762be5380f1b383b726211ef7f96
Tx public key: 41cfed5957dc837058ffe3c0f4dc9da033dd1e8dcc8045e532d0579eaeea33d4
Timestamp: 1703445531 Timestamp [UCT]: 2023-12-24 19:18:51 Age [y:d:h:m:s]: 02:010:22:22:02
Block: 920317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527588 RingCT/type: yes/0
Extra: 0141cfed5957dc837058ffe3c0f4dc9da033dd1e8dcc8045e532d0579eaeea33d40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2b847f5d916215deae835af89a67a007b3fce0ee41068a9f1c99c6e1120f73d 0.600000000000 1377995 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": 920327, "vin": [ { "gen": { "height": 920317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2b847f5d916215deae835af89a67a007b3fce0ee41068a9f1c99c6e1120f73d" } } ], "extra": [ 1, 65, 207, 237, 89, 87, 220, 131, 112, 88, 255, 227, 192, 244, 220, 157, 160, 51, 221, 30, 141, 204, 128, 69, 229, 50, 208, 87, 158, 174, 234, 51, 212, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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