Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5715db0dd23b16d62bded9b42719be3339a02a68f2142f07bd491018750b9c

Tx prefix hash: 68a2764556019caf66b1dc9af087f45e1ea5bb36f0fa190d52a9a44daf83f9aa
Tx public key: f44299d924e9ba089a088110342bf0fd31fcacf9f6455a1c3b606455c814a1f3
Timestamp: 1761876101 Timestamp [UCT]: 2025-10-31 02:01:41 Age [y:d:h:m:s]: 00:020:05:59:48
Block: 1401620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14487 RingCT/type: yes/0
Extra: 01f44299d924e9ba089a088110342bf0fd31fcacf9f6455a1c3b606455c814a1f3021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d6d451dba5033b49cc013fa6a7b92aad920a4d6e250167de24719b455698534 0.600000000000 1889939 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": 1401630, "vin": [ { "gen": { "height": 1401620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d6d451dba5033b49cc013fa6a7b92aad920a4d6e250167de24719b455698534" } } ], "extra": [ 1, 244, 66, 153, 217, 36, 233, 186, 8, 154, 8, 129, 16, 52, 43, 240, 253, 49, 252, 172, 249, 246, 69, 90, 28, 59, 96, 100, 85, 200, 20, 161, 243, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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