Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc5fd1c337f108139dbf236333e7544f45a7bcf5510843564e1d0f32382a2f12

Tx prefix hash: 5fa7aa0d36069f1bb1afcc4af5cef00e734830d5ad377a4a9880e34e484fc561
Tx public key: 4037500e4040830753c0ddd566c181e7c4dda64b8406a70b1dc6694403ca6be6
Timestamp: 1709204816 Timestamp [UCT]: 2024-02-29 11:06:56 Age [y:d:h:m:s]: 00:332:19:30:37
Block: 968063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237998 RingCT/type: yes/0
Extra: 014037500e4040830753c0ddd566c181e7c4dda64b8406a70b1dc6694403ca6be602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ee446aa4ae14f02803df757e3c52b6ae0bc46d39154f74fbe6b1ba0ebfd67d7 0.600000000000 1427860 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": 968073, "vin": [ { "gen": { "height": 968063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ee446aa4ae14f02803df757e3c52b6ae0bc46d39154f74fbe6b1ba0ebfd67d7" } } ], "extra": [ 1, 64, 55, 80, 14, 64, 64, 131, 7, 83, 192, 221, 213, 102, 193, 129, 231, 196, 221, 166, 75, 132, 6, 167, 11, 29, 198, 105, 68, 3, 202, 107, 230, 2, 17, 0, 0, 0, 5, 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