Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64fc1c8d4c8c0682a118be8c4ce7e9557fd0f4841e8156c4750e22db571ecacf

Tx prefix hash: 2fd7222cfe4755f086cc40b144c41f9d3723c8f2be03d24fbba547ef213db622
Tx public key: ee3ca35245242a3d2870e70c5bac7b3e60e780a74718d510ef8ab2985be1d6ae
Timestamp: 1762006916 Timestamp [UCT]: 2025-11-01 14:21:56 Age [y:d:h:m:s]: 00:005:11:21:33
Block: 1402719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3883 RingCT/type: yes/0
Extra: 01ee3ca35245242a3d2870e70c5bac7b3e60e780a74718d510ef8ab2985be1d6ae021100000007df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df4d57e683da77bb34a76bcc93b8202dc5a1a96a12eea0c5abb3aeec9eb76f35 0.600000000000 1891038 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": 1402729, "vin": [ { "gen": { "height": 1402719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df4d57e683da77bb34a76bcc93b8202dc5a1a96a12eea0c5abb3aeec9eb76f35" } } ], "extra": [ 1, 238, 60, 163, 82, 69, 36, 42, 61, 40, 112, 231, 12, 91, 172, 123, 62, 96, 231, 128, 167, 71, 24, 213, 16, 239, 138, 178, 152, 91, 225, 214, 174, 2, 17, 0, 0, 0, 7, 223, 90, 36, 122, 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