Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0039406d7ef7ab6b930feb09f281d0a8ebda19139ec0e55c4b89ed7baa41038f

Tx prefix hash: 60783d0d9409f796cabfcddebfe17cac5d252137dad720ba504b6c1e27192b04
Tx public key: 21a60c77cfc6a9f2b159853ba552ed00f9d7b0ab1db19a10323fd29847f63c0e
Timestamp: 1751658400 Timestamp [UCT]: 2025-07-04 19:46:40 Age [y:d:h:m:s]: 00:132:08:59:18
Block: 1318804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92908 RingCT/type: yes/0
Extra: 0121a60c77cfc6a9f2b159853ba552ed00f9d7b0ab1db19a10323fd29847f63c0e02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6245b438ad37fb061ca7b2073f9a5543e060229c5a97b056a143720aa4f4768 0.600000000000 1806491 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": 1318814, "vin": [ { "gen": { "height": 1318804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6245b438ad37fb061ca7b2073f9a5543e060229c5a97b056a143720aa4f4768" } } ], "extra": [ 1, 33, 166, 12, 119, 207, 198, 169, 242, 177, 89, 133, 59, 165, 82, 237, 0, 249, 215, 176, 171, 29, 177, 154, 16, 50, 63, 210, 152, 71, 246, 60, 14, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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