Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2c2d62baf024e63010fc018057b9447c2aa56725d9c7a212089f809969715b5

Tx prefix hash: 62d3fb0c4159b19e0c8830d6f11f485b0d2454efe37dc43b87305e2a073c5913
Tx public key: ef73a364f7663bbe72fcef4e8ac7bc82af8cd09c5aaf2057dfcdae481dc18829
Timestamp: 1730558009 Timestamp [UCT]: 2024-11-02 14:33:29 Age [y:d:h:m:s]: 00:137:07:41:31
Block: 1145002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97994 RingCT/type: yes/0
Extra: 01ef73a364f7663bbe72fcef4e8ac7bc82af8cd09c5aaf2057dfcdae481dc188290211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68e371ae6173b4d20777da3f236986781dceefae91adfd4a8aa9f6d4afe02567 0.600000000000 1629359 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": 1145012, "vin": [ { "gen": { "height": 1145002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68e371ae6173b4d20777da3f236986781dceefae91adfd4a8aa9f6d4afe02567" } } ], "extra": [ 1, 239, 115, 163, 100, 247, 102, 59, 190, 114, 252, 239, 78, 138, 199, 188, 130, 175, 140, 208, 156, 90, 175, 32, 87, 223, 205, 174, 72, 29, 193, 136, 41, 2, 17, 0, 0, 0, 4, 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