Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4349a400cae91762accad7db2e9d000457ab0f138b6af32a8604910827c30b96

Tx prefix hash: 4c403f9c8221e7138b78d0a76da9528565ccec8edb04f06eff4bef2e9b9755c0
Tx public key: 9370c7a4e59de30662fd8fa6fb62379d3d1c1a9a4bfcec0879f0ce811d05dc27
Timestamp: 1711830037 Timestamp [UCT]: 2024-03-30 20:20:37 Age [y:d:h:m:s]: 01:077:22:40:17
Block: 989838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316588 RingCT/type: yes/0
Extra: 019370c7a4e59de30662fd8fa6fb62379d3d1c1a9a4bfcec0879f0ce811d05dc2702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23c8bd9faabbbb00a594fe3081587dba075c141ebbf807137beb7e02ee67cbe2 0.600000000000 1450156 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": 989848, "vin": [ { "gen": { "height": 989838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23c8bd9faabbbb00a594fe3081587dba075c141ebbf807137beb7e02ee67cbe2" } } ], "extra": [ 1, 147, 112, 199, 164, 229, 157, 227, 6, 98, 253, 143, 166, 251, 98, 55, 157, 61, 28, 26, 154, 75, 252, 236, 8, 121, 240, 206, 129, 29, 5, 220, 39, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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