Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fe9a930c0651e6ca33c7746bcc3dfd32da29c97b73271009d02aa2c2975625d

Tx prefix hash: f2767164988a1ea6c813620fc85bc5d3cff01083a15b26a32b77a6b8962d8882
Tx public key: 5c52067b73c4079e9a5250c6f9fbe8f60158444b34e5c1546a56c380291483f7
Timestamp: 1758269293 Timestamp [UCT]: 2025-09-19 08:08:13 Age [y:d:h:m:s]: 00:102:13:45:00
Block: 1371718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73434 RingCT/type: yes/0
Extra: 015c52067b73c4079e9a5250c6f9fbe8f60158444b34e5c1546a56c380291483f7021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0d2acdd8b59ed1589a5986fa9972be3f05ab15f4ac9a9b9caea4b6436ffaadb 0.600000000000 1859795 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": 1371728, "vin": [ { "gen": { "height": 1371718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0d2acdd8b59ed1589a5986fa9972be3f05ab15f4ac9a9b9caea4b6436ffaadb" } } ], "extra": [ 1, 92, 82, 6, 123, 115, 196, 7, 158, 154, 82, 80, 198, 249, 251, 232, 246, 1, 88, 68, 75, 52, 229, 193, 84, 106, 86, 195, 128, 41, 20, 131, 247, 2, 17, 0, 0, 0, 3, 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