Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cdcd9c85372e5a5f6be094dc89eed68b06a1e90a23652783237d78c144d5264

Tx prefix hash: 17dc8bd7d4a9aa8cef65e06cfd252418054b639c1ac76b232a10acc230776b23
Tx public key: 78ac63b22896f6b3bafa53eb3359540d4dfe6b889e7addc1d6dbc3aec066775e
Timestamp: 1704838150 Timestamp [UCT]: 2024-01-09 22:09:10 Age [y:d:h:m:s]: 01:108:15:50:16
Block: 931843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338787 RingCT/type: yes/0
Extra: 0178ac63b22896f6b3bafa53eb3359540d4dfe6b889e7addc1d6dbc3aec066775e02110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9168b2df25fd511dbae05605a0deb867e5f6aaaeb319b94a68936fa91efabd1 0.600000000000 1389747 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": 931853, "vin": [ { "gen": { "height": 931843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9168b2df25fd511dbae05605a0deb867e5f6aaaeb319b94a68936fa91efabd1" } } ], "extra": [ 1, 120, 172, 99, 178, 40, 150, 246, 179, 186, 250, 83, 235, 51, 89, 84, 13, 77, 254, 107, 136, 158, 122, 221, 193, 214, 219, 195, 174, 192, 102, 119, 94, 2, 17, 0, 0, 0, 13, 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