Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa2e07d145b2dd22d9effda473133ec531fcfd05a487f0acb06cb7b628e6c3d7

Tx prefix hash: 94e3819df4280d322125ce7a05a24f65de2eb6ceae2b9eaa473113318e774cdb
Tx public key: b599d44bfe1cc6c0ae2fcc02bee8cc6e85d687860378e6bd7c8267aa5ce0620d
Timestamp: 1733054546 Timestamp [UCT]: 2024-12-01 12:02:26 Age [y:d:h:m:s]: 00:123:10:08:05
Block: 1165689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87992 RingCT/type: yes/0
Extra: 01b599d44bfe1cc6c0ae2fcc02bee8cc6e85d687860378e6bd7c8267aa5ce0620d0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72cd10f900fa2965957417ccd30046479da3068e607e75d25230d883a2075536 0.600000000000 1651364 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": 1165699, "vin": [ { "gen": { "height": 1165689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72cd10f900fa2965957417ccd30046479da3068e607e75d25230d883a2075536" } } ], "extra": [ 1, 181, 153, 212, 75, 254, 28, 198, 192, 174, 47, 204, 2, 190, 232, 204, 110, 133, 214, 135, 134, 3, 120, 230, 189, 124, 130, 103, 170, 92, 224, 98, 13, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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