Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba4b61d31fe28b60d44a6c95c60d25c153677331a0b4462b2838ed9d634a33ea

Tx prefix hash: d9295cf8a8de33d3e1097db4bc37dce4298ac61ee4fb349959f2bb83df55336e
Tx public key: 67811322075714bcab5fb1056cb077abb55766cb1aa77a6344e65f6b333c4be0
Timestamp: 1730198700 Timestamp [UCT]: 2024-10-29 10:45:00 Age [y:d:h:m:s]: 00:147:08:51:49
Block: 1142052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105123 RingCT/type: yes/0
Extra: 0167811322075714bcab5fb1056cb077abb55766cb1aa77a6344e65f6b333c4be0021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8472992f47f8d5c8b4fe9263597b3cb45d51c0d7057c12a898b221ae3a318413 0.600000000000 1625887 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": 1142062, "vin": [ { "gen": { "height": 1142052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8472992f47f8d5c8b4fe9263597b3cb45d51c0d7057c12a898b221ae3a318413" } } ], "extra": [ 1, 103, 129, 19, 34, 7, 87, 20, 188, 171, 95, 177, 5, 108, 176, 119, 171, 181, 87, 102, 203, 26, 167, 122, 99, 68, 230, 95, 107, 51, 60, 75, 224, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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