Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88e853a93a6f1e140c2cc25eeeb5d3a42553cc4e7ab708bd120def8541c418a6

Tx prefix hash: ddb99e615db3bf368346134a6eeec371863a023447cae30056fc89e373b13c9a
Tx public key: de7291b87a9a2807aaa31f4b1f7016379aa87a175b13b0eb04fb88c67464e8d9
Timestamp: 1706615459 Timestamp [UCT]: 2024-01-30 11:50:59 Age [y:d:h:m:s]: 01:067:16:40:17
Block: 946571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309449 RingCT/type: yes/0
Extra: 01de7291b87a9a2807aaa31f4b1f7016379aa87a175b13b0eb04fb88c67464e8d90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a08d5ffbad57c3cb213e93f1b2d2cd3f23906a424e5d129ab82cd3d3282da0 0.600000000000 1404903 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": 946581, "vin": [ { "gen": { "height": 946571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a08d5ffbad57c3cb213e93f1b2d2cd3f23906a424e5d129ab82cd3d3282da0" } } ], "extra": [ 1, 222, 114, 145, 184, 122, 154, 40, 7, 170, 163, 31, 75, 31, 112, 22, 55, 154, 168, 122, 23, 91, 19, 176, 235, 4, 251, 136, 198, 116, 100, 232, 217, 2, 17, 0, 0, 0, 1, 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