Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ed2d857440e1363a3e409fcdcbc27236ef2677793bd59addd431e67ea90e674

Tx prefix hash: 925b8e36425bec409f364009bc49038a513abcb762296fa52f8eebf946aa8ebd
Tx public key: d5795451f0fa0a6d0c1eba0c45878b75b72b84569226e610a2d69f4d5a72d54b
Timestamp: 1700774496 Timestamp [UCT]: 2023-11-23 21:21:36 Age [y:d:h:m:s]: 01:195:10:10:16
Block: 898157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400897 RingCT/type: yes/0
Extra: 01d5795451f0fa0a6d0c1eba0c45878b75b72b84569226e610a2d69f4d5a72d54b02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.648683726000 dcy

stealth address amount amount idx
00: e9f14246a89c5f65c70e5f754e9442b1966f9e437b57ae0e3c7fccfdc544892a 0.648683726000 1354562 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": 898167, "vin": [ { "gen": { "height": 898157 } } ], "vout": [ { "amount": 648683726, "target": { "key": "e9f14246a89c5f65c70e5f754e9442b1966f9e437b57ae0e3c7fccfdc544892a" } } ], "extra": [ 1, 213, 121, 84, 81, 240, 250, 10, 109, 12, 30, 186, 12, 69, 135, 139, 117, 183, 43, 132, 86, 146, 38, 230, 16, 162, 214, 159, 77, 90, 114, 213, 75, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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