Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76fe7e4045b961024961a4ce8d2ab08959b7cc20745d7868a297d2a82a53d22d

Tx prefix hash: fca10ef381373842f594e74b270cddf6b4f0265e51f714e31e2c66f076dccf78
Tx public key: 0b2d9de45e74f90054fb59ba9511eff1eb624a5ad7edab9f548ca5ed7cd6d1a1
Timestamp: 1705422206 Timestamp [UCT]: 2024-01-16 16:23:26 Age [y:d:h:m:s]: 01:294:20:36:11
Block: 936678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469537 RingCT/type: yes/0
Extra: 010b2d9de45e74f90054fb59ba9511eff1eb624a5ad7edab9f548ca5ed7cd6d1a10211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 094cb8e446c3e6050b2df930e3b57982430d1717f300530e660828758ffbaf70 0.600000000000 1394716 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": 936688, "vin": [ { "gen": { "height": 936678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "094cb8e446c3e6050b2df930e3b57982430d1717f300530e660828758ffbaf70" } } ], "extra": [ 1, 11, 45, 157, 228, 94, 116, 249, 0, 84, 251, 89, 186, 149, 17, 239, 241, 235, 98, 74, 90, 215, 237, 171, 159, 84, 140, 165, 237, 124, 214, 209, 161, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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