Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4d009bf741a45b1e1234979df8b86512a4df7e80896b2d50657d4b017216c39

Tx prefix hash: a5c3ff646f4b1b3415db87adb25313d7ed24252e3ba468297a1ed10d023ad751
Tx public key: 203a0f0d7d760982241513ddc2f2612fde85e1c053bdf3a934f88d5347fa90cc
Timestamp: 1750352813 Timestamp [UCT]: 2025-06-19 17:06:53 Age [y:d:h:m:s]: 00:153:21:15:30
Block: 1308499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107787 RingCT/type: yes/0
Extra: 01203a0f0d7d760982241513ddc2f2612fde85e1c053bdf3a934f88d5347fa90cc021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c0f10240f971e0591bfc609df534c2d06767d09595cfce20def43d9768269ab 0.600000000000 1796112 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": 1308509, "vin": [ { "gen": { "height": 1308499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c0f10240f971e0591bfc609df534c2d06767d09595cfce20def43d9768269ab" } } ], "extra": [ 1, 32, 58, 15, 13, 125, 118, 9, 130, 36, 21, 19, 221, 194, 242, 97, 47, 222, 133, 225, 192, 83, 189, 243, 169, 52, 248, 141, 83, 71, 250, 144, 204, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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