Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1087c3a3e2a1edec762294d7d8052deccf8c4d461a88d77c4d541739229d90ec

Tx prefix hash: 2ad48b38256d06fc6ec95de9febd812b044924576a0bfc897ae1c4358210b476
Tx public key: 1295ca527f12a009e5f7ca0dd6412c92e977f8c716a58b390c968d36598f1b44
Timestamp: 1755884897 Timestamp [UCT]: 2025-08-22 17:48:17 Age [y:d:h:m:s]: 00:058:01:42:18
Block: 1352136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41420 RingCT/type: yes/0
Extra: 011295ca527f12a009e5f7ca0dd6412c92e977f8c716a58b390c968d36598f1b440211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6501e0a8a82e7416f4213ab0ea8f4665b27f8210b0070f5a9e12f47a237fd523 0.600000000000 1840099 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": 1352146, "vin": [ { "gen": { "height": 1352136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6501e0a8a82e7416f4213ab0ea8f4665b27f8210b0070f5a9e12f47a237fd523" } } ], "extra": [ 1, 18, 149, 202, 82, 127, 18, 160, 9, 229, 247, 202, 13, 214, 65, 44, 146, 233, 119, 248, 199, 22, 165, 139, 57, 12, 150, 141, 54, 89, 143, 27, 68, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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