Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57d32232940590af733452ff1d25f0cfa42896d7ebb07eed0024c5a94bddefec

Tx prefix hash: f0548996341df0127339e9d98800e52f9de05c2f82f417819f9f62c3a8b381b5
Tx public key: 3f01cee5bc5b34d93e3af70c7668677953d432f69fd8a3db5bda93711c9ef925
Timestamp: 1736412793 Timestamp [UCT]: 2025-01-09 08:53:13 Age [y:d:h:m:s]: 00:161:04:39:52
Block: 1193490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114905 RingCT/type: yes/0
Extra: 013f01cee5bc5b34d93e3af70c7668677953d432f69fd8a3db5bda93711c9ef925021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d63f7fa196e9edc7fe2dca287f173771be50ad708c301ed6367b7ef3dc7e5c27 0.600000000000 1680051 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": 1193500, "vin": [ { "gen": { "height": 1193490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d63f7fa196e9edc7fe2dca287f173771be50ad708c301ed6367b7ef3dc7e5c27" } } ], "extra": [ 1, 63, 1, 206, 229, 188, 91, 52, 217, 62, 58, 247, 12, 118, 104, 103, 121, 83, 212, 50, 246, 159, 216, 163, 219, 91, 218, 147, 113, 28, 158, 249, 37, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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