Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e743b19cd8abe26bd9827c5455f370c84d51cf26f5ac5972ddb016d9f44ad9b

Tx prefix hash: 7c8d635399dceabc9209867536fefc8dc394b491a4c0d2d00692b739a64079a3
Tx public key: 290ab0a837d6515e6cddb621e4e7f9a850eaaa23ffa2a0e4a97c4afba85b05bd
Timestamp: 1721001745 Timestamp [UCT]: 2024-07-15 00:02:25 Age [y:d:h:m:s]: 00:314:18:41:40
Block: 1065874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224927 RingCT/type: yes/0
Extra: 01290ab0a837d6515e6cddb621e4e7f9a850eaaa23ffa2a0e4a97c4afba85b05bd02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 349ba9da909c645d44b5953cde7cccdf2fd84d65b9c613e9142e5fca4b0e7500 0.600000000000 1536443 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": 1065884, "vin": [ { "gen": { "height": 1065874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "349ba9da909c645d44b5953cde7cccdf2fd84d65b9c613e9142e5fca4b0e7500" } } ], "extra": [ 1, 41, 10, 176, 168, 55, 214, 81, 94, 108, 221, 182, 33, 228, 231, 249, 168, 80, 234, 170, 35, 255, 162, 160, 228, 169, 124, 74, 251, 168, 91, 5, 189, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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