Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4245b40b6d67532ac6ae2b81475fff2a6ee237c8db38431f48649cd56f64a178

Tx prefix hash: 865952460828d827b1c817a107657cea7c6824b6c9209dd0e4cb77a5d4797fc3
Tx public key: 7938e03630c3c28a95ad82e53f7a4a82020d4e87eb7239e65bcb1e4533953c12
Timestamp: 1754321271 Timestamp [UCT]: 2025-08-04 15:27:51 Age [y:d:h:m:s]: 00:076:04:02:44
Block: 1340187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53369 RingCT/type: yes/0
Extra: 017938e03630c3c28a95ad82e53f7a4a82020d4e87eb7239e65bcb1e4533953c1202110000000ab2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 561b15f7b4505561321c1508f765fb97329fcd2095ac8e0e485c0ba1a2e19da3 0.600000000000 1828004 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": 1340197, "vin": [ { "gen": { "height": 1340187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "561b15f7b4505561321c1508f765fb97329fcd2095ac8e0e485c0ba1a2e19da3" } } ], "extra": [ 1, 121, 56, 224, 54, 48, 195, 194, 138, 149, 173, 130, 229, 63, 122, 74, 130, 2, 13, 78, 135, 235, 114, 57, 230, 91, 203, 30, 69, 51, 149, 60, 18, 2, 17, 0, 0, 0, 10, 178, 247, 132, 196, 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