Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50c68caa1a77492847470fc6e5b65eaf846525d9a4aa7c9a4bb15cc60125934c

Tx prefix hash: 62e4e6c3f0b0ca8f6fa4ae34f23fbfdc7834912e72be64fa0983b2cb711820da
Tx public key: 94ab486c314d059cf437e0f99e521d2b9865cc6b5b8345a63202e661fe65c74b
Timestamp: 1703110165 Timestamp [UCT]: 2023-12-20 22:09:25 Age [y:d:h:m:s]: 01:293:11:05:21
Block: 917549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468518 RingCT/type: yes/0
Extra: 0194ab486c314d059cf437e0f99e521d2b9865cc6b5b8345a63202e661fe65c74b021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a640958231f5cf183c46aa4af57300756aeeb34ac44ac822a81d71eb8e0d9915 0.600000000000 1375131 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": 917559, "vin": [ { "gen": { "height": 917549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a640958231f5cf183c46aa4af57300756aeeb34ac44ac822a81d71eb8e0d9915" } } ], "extra": [ 1, 148, 171, 72, 108, 49, 77, 5, 156, 244, 55, 224, 249, 158, 82, 29, 43, 152, 101, 204, 107, 91, 131, 69, 166, 50, 2, 230, 97, 254, 101, 199, 75, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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