Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0742cde77b1f14d5e217c6ba3d2456916a0b8213358ffebfa18e6f587514a38

Tx prefix hash: 226398fa35e0af41564863b7c691f5bda58811469ab8d5a3aaf2d52a688adc07
Tx public key: 23ba51c5b3d03c1ac39e60b74dd55d34b44b05c701f3b8f6c36f7934ca770aa9
Timestamp: 1712329556 Timestamp [UCT]: 2024-04-05 15:05:56 Age [y:d:h:m:s]: 01:209:04:33:18
Block: 993937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408205 RingCT/type: yes/0
Extra: 0123ba51c5b3d03c1ac39e60b74dd55d34b44b05c701f3b8f6c36f7934ca770aa902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93bc8f1aafec37ec214e285fd70c289b6766aebdefa41b6847dadd7dfc9c9b69 0.600000000000 1454333 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": 993947, "vin": [ { "gen": { "height": 993937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93bc8f1aafec37ec214e285fd70c289b6766aebdefa41b6847dadd7dfc9c9b69" } } ], "extra": [ 1, 35, 186, 81, 197, 179, 208, 60, 26, 195, 158, 96, 183, 77, 213, 93, 52, 180, 75, 5, 199, 1, 243, 184, 246, 195, 111, 121, 52, 202, 119, 10, 169, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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