Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 386487cd46e2b7f3f2133a6cecda329b30ae5f33e23089b4767bcae8d0eaaeca

Tx prefix hash: f2aa5f807e75cff1372a1dbd36c5551e300aaf501dcb31037077852725aa2852
Tx public key: 5e26c67506ae16cf217393324e53eecb7a6bb3699a8efdb88ddd6dff55e08e49
Timestamp: 1729259192 Timestamp [UCT]: 2024-10-18 13:46:32 Age [y:d:h:m:s]: 00:020:14:13:28
Block: 1134324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14660 RingCT/type: yes/0
Extra: 015e26c67506ae16cf217393324e53eecb7a6bb3699a8efdb88ddd6dff55e08e490211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae0bad1e4181a8a081232d3bc378979cac63086118356b0671ef3fd31e8cbf03 0.600000000000 1617615 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": 1134334, "vin": [ { "gen": { "height": 1134324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae0bad1e4181a8a081232d3bc378979cac63086118356b0671ef3fd31e8cbf03" } } ], "extra": [ 1, 94, 38, 198, 117, 6, 174, 22, 207, 33, 115, 147, 50, 78, 83, 238, 203, 122, 107, 179, 105, 154, 142, 253, 184, 141, 221, 109, 255, 85, 224, 142, 73, 2, 17, 0, 0, 0, 3, 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