Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e74be88feb0494de7661e58e483145cfe8367f8369c6b86f767385031c6f6e92

Tx prefix hash: 34ad8025e4d3d0c52ca9636f32580d118fb8e6128c251627b6f71af634f023cf
Tx public key: 526f1da83f7d5493e8511b77f7c35b6e730061414fce51ad2858b38cf412c7c5
Timestamp: 1739581622 Timestamp [UCT]: 2025-02-15 01:07:02 Age [y:d:h:m:s]: 00:027:11:23:19
Block: 1219467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19663 RingCT/type: yes/0
Extra: 01526f1da83f7d5493e8511b77f7c35b6e730061414fce51ad2858b38cf412c7c50211000000248377ed96000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf7c36f513a713ab3a107c1af9f7d08617f3bb1ef42c2899adf242a5b2b11822 0.600000000000 1706292 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": 1219477, "vin": [ { "gen": { "height": 1219467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf7c36f513a713ab3a107c1af9f7d08617f3bb1ef42c2899adf242a5b2b11822" } } ], "extra": [ 1, 82, 111, 29, 168, 63, 125, 84, 147, 232, 81, 27, 119, 247, 195, 91, 110, 115, 0, 97, 65, 79, 206, 81, 173, 40, 88, 179, 140, 244, 18, 199, 197, 2, 17, 0, 0, 0, 36, 131, 119, 237, 150, 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