Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98d9f39e3ecc75a94181130ff521dcc6966c5c196324a58ffa65d6d20c92578b

Tx prefix hash: 41625177b8b20f0f56ba6bd28be99929eb36a13e69a1552669d075206ea35d6c
Tx public key: 66ddcab1dbaf8cae1eeb8b6be36ea9581fbc261d784a5cdf7a839cfaef5a53fb
Timestamp: 1705016379 Timestamp [UCT]: 2024-01-11 23:39:39 Age [y:d:h:m:s]: 01:082:02:02:38
Block: 933314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319764 RingCT/type: yes/0
Extra: 0166ddcab1dbaf8cae1eeb8b6be36ea9581fbc261d784a5cdf7a839cfaef5a53fb0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4722ba59056bd5bf124ef703f160666279ae4b1b16082802c59a24e9fcc5a81b 0.600000000000 1391276 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": 933324, "vin": [ { "gen": { "height": 933314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4722ba59056bd5bf124ef703f160666279ae4b1b16082802c59a24e9fcc5a81b" } } ], "extra": [ 1, 102, 221, 202, 177, 219, 175, 140, 174, 30, 235, 139, 107, 227, 110, 169, 88, 31, 188, 38, 29, 120, 74, 92, 223, 122, 131, 156, 250, 239, 90, 83, 251, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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