Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4e5e12dcc315c7cf16ee5153d0c9d2778d77fd92dcdcc204ee7c793fd5f8696

Tx prefix hash: 8f1c737d0e396945ec96bc2e100a0cbfa59735099732f05764e659f58146ad86
Tx public key: 7bae1cbccf5ade082426c8ed627986c96f68217b9b1e1e1a541f1feb349d68bf
Timestamp: 1714746390 Timestamp [UCT]: 2024-05-03 14:26:30 Age [y:d:h:m:s]: 00:250:22:49:12
Block: 1014003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179623 RingCT/type: yes/0
Extra: 017bae1cbccf5ade082426c8ed627986c96f68217b9b1e1e1a541f1feb349d68bf0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a30b16c18a4c06284849e81a0458173dd9e80c92a353e0ad92254cf8921193b9 0.600000000000 1476974 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": 1014013, "vin": [ { "gen": { "height": 1014003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a30b16c18a4c06284849e81a0458173dd9e80c92a353e0ad92254cf8921193b9" } } ], "extra": [ 1, 123, 174, 28, 188, 207, 90, 222, 8, 36, 38, 200, 237, 98, 121, 134, 201, 111, 104, 33, 123, 155, 30, 30, 26, 84, 31, 31, 235, 52, 157, 104, 191, 2, 17, 0, 0, 0, 2, 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