Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f747db6b4e2fa299353ffed82cd1fb30aeb61313b1454635dc81514a2e6d289

Tx prefix hash: 78a999f72239ad009e5ce4ea765d8312be1c96de211909aa126570a09fbe4539
Tx public key: f1ed90710877b0f0ca59fc2998628c7f3aa39da04b7ca2dc210f590dfe2277c5
Timestamp: 1710159797 Timestamp [UCT]: 2024-03-11 12:23:17 Age [y:d:h:m:s]: 01:081:19:26:51
Block: 975994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319501 RingCT/type: yes/0
Extra: 01f1ed90710877b0f0ca59fc2998628c7f3aa39da04b7ca2dc210f590dfe2277c50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 362515bb2d460258ae9a519ce469bd45d6c2f9aa79098d962e18197e92b8d5cf 0.600000000000 1435975 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": 976004, "vin": [ { "gen": { "height": 975994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "362515bb2d460258ae9a519ce469bd45d6c2f9aa79098d962e18197e92b8d5cf" } } ], "extra": [ 1, 241, 237, 144, 113, 8, 119, 176, 240, 202, 89, 252, 41, 152, 98, 140, 127, 58, 163, 157, 160, 75, 124, 162, 220, 33, 15, 89, 13, 254, 34, 119, 197, 2, 17, 0, 0, 0, 4, 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