Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d11e141a60001419003c521c7cdefc76e2b5271102d315b18a40b5563955be9

Tx prefix hash: 53eabe8241a00163da8d590750fd6e8cc6500e91146811cbde955180cd25be71
Tx public key: 0c9c8e5c74e3e73f0fd4b75d12bd9420cdceb32e75ab81a57f255283c237dfee
Timestamp: 1737414428 Timestamp [UCT]: 2025-01-20 23:07:08 Age [y:d:h:m:s]: 00:149:23:40:28
Block: 1201737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106916 RingCT/type: yes/0
Extra: 010c9c8e5c74e3e73f0fd4b75d12bd9420cdceb32e75ab81a57f255283c237dfee0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6182bf8003f7d22632be62dcc4cbd8b5ecf9b523aac5990b82adcfc5dd4bcb08 0.600000000000 1688394 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": 1201747, "vin": [ { "gen": { "height": 1201737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6182bf8003f7d22632be62dcc4cbd8b5ecf9b523aac5990b82adcfc5dd4bcb08" } } ], "extra": [ 1, 12, 156, 142, 92, 116, 227, 231, 63, 15, 212, 183, 93, 18, 189, 148, 32, 205, 206, 179, 46, 117, 171, 129, 165, 127, 37, 82, 131, 194, 55, 223, 238, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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