Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a00316deecf18ecc397993927bbb16c7501ecfe0c78155f3f630ceaa10896ca

Tx prefix hash: e064407c4e7db806e5a50284ec6f2323f1584e5ab6bed9d8d7f0db46a4250f3e
Tx public key: 9fd687f6779f3a9cc1e9bb91e03bd3cf501aa72d8411402d12cfeac89d7354d9
Timestamp: 1701593334 Timestamp [UCT]: 2023-12-03 08:48:54 Age [y:d:h:m:s]: 01:082:07:23:30
Block: 904952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319937 RingCT/type: yes/0
Extra: 019fd687f6779f3a9cc1e9bb91e03bd3cf501aa72d8411402d12cfeac89d7354d902110000000775e3f0e9000000000000000000

1 output(s) for total of 0.615911533000 dcy

stealth address amount amount idx
00: cd6b8d2ea35a8ceeff6f6a0df9219500e946ae5fbc4a83d239cd3df2cfbf6ecc 0.615911533000 1361767 of 0

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": 904962, "vin": [ { "gen": { "height": 904952 } } ], "vout": [ { "amount": 615911533, "target": { "key": "cd6b8d2ea35a8ceeff6f6a0df9219500e946ae5fbc4a83d239cd3df2cfbf6ecc" } } ], "extra": [ 1, 159, 214, 135, 246, 119, 159, 58, 156, 193, 233, 187, 145, 224, 59, 211, 207, 80, 26, 167, 45, 132, 17, 64, 45, 18, 207, 234, 200, 157, 115, 84, 217, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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