Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64fc5df20cb5924ae9c92f83ba006a980590bfffdc107483a2f768c228fe2e65

Tx prefix hash: 0c6c8855ae9afdc311d6620a4a09fbc72c23613944efebb030e350b602654e1f
Tx public key: 7203f30741169f59a971a12e49f60fba900b1c7d2a31579dffab77561f5a70cb
Timestamp: 1737399970 Timestamp [UCT]: 2025-01-20 19:06:10 Age [y:d:h:m:s]: 00:148:17:31:55
Block: 1201619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106040 RingCT/type: yes/0
Extra: 017203f30741169f59a971a12e49f60fba900b1c7d2a31579dffab77561f5a70cb0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abb8a6cc8b8eb6110bedd8f2e9cdff1caac3b16771d5c04f4ea773ac12b2ef60 0.600000000000 1688274 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": 1201629, "vin": [ { "gen": { "height": 1201619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abb8a6cc8b8eb6110bedd8f2e9cdff1caac3b16771d5c04f4ea773ac12b2ef60" } } ], "extra": [ 1, 114, 3, 243, 7, 65, 22, 159, 89, 169, 113, 161, 46, 73, 246, 15, 186, 144, 11, 28, 125, 42, 49, 87, 157, 255, 171, 119, 86, 31, 90, 112, 203, 2, 17, 0, 0, 0, 2, 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