Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28a67c115d7c2cd5cc0cbbeecd03919cd70e6bd5c92831d78770fd0929d1c00a

Tx prefix hash: d38c9376f47795f7d16493b98c52c79249d2a7a080187be0651c16f24e40504e
Tx public key: ef2da73fa1b2b250607bb240fc3459e58e5e5b56a9845a62b65c97dd8cbbc3c6
Timestamp: 1755066641 Timestamp [UCT]: 2025-08-13 06:30:41 Age [y:d:h:m:s]: 00:097:03:35:22
Block: 1345872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68868 RingCT/type: yes/0
Extra: 01ef2da73fa1b2b250607bb240fc3459e58e5e5b56a9845a62b65c97dd8cbbc3c60211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e47c7fd9e03d6ce7a7cc3d091bdc9bec10e90d5c66120eeaee2f70286843de1 0.600000000000 1833769 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": 1345882, "vin": [ { "gen": { "height": 1345872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e47c7fd9e03d6ce7a7cc3d091bdc9bec10e90d5c66120eeaee2f70286843de1" } } ], "extra": [ 1, 239, 45, 167, 63, 161, 178, 178, 80, 96, 123, 178, 64, 252, 52, 89, 229, 142, 94, 91, 86, 169, 132, 90, 98, 182, 92, 151, 221, 140, 187, 195, 198, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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