Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 335fd4738005bb3d93d05d6429682fa4ecfe98e5265f824ffe31e039aeb78181

Tx prefix hash: 2e91af9f431e3bcdc8915094a6150094ac42b394e55571221d3331ee3711093f
Tx public key: 0aac5e3be4db20d145d2e616e369d71fd29d1e502dfcfa653e943f10d2d602d6
Timestamp: 1722416748 Timestamp [UCT]: 2024-07-31 09:05:48 Age [y:d:h:m:s]: 00:253:14:02:36
Block: 1077587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181144 RingCT/type: yes/0
Extra: 010aac5e3be4db20d145d2e616e369d71fd29d1e502dfcfa653e943f10d2d602d602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2c1effa91a0d240cc7ce510ad724c4d8fbd1177f54961bdae3848b99938086d 0.600000000000 1550138 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": 1077597, "vin": [ { "gen": { "height": 1077587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2c1effa91a0d240cc7ce510ad724c4d8fbd1177f54961bdae3848b99938086d" } } ], "extra": [ 1, 10, 172, 94, 59, 228, 219, 32, 209, 69, 210, 230, 22, 227, 105, 215, 31, 210, 157, 30, 80, 45, 252, 250, 101, 62, 148, 63, 16, 210, 214, 2, 214, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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