Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c7f5066b7ca5e0225e6dedf21f751d4ea27554569136f52036fc2e8cf362b10

Tx prefix hash: 0bbe47dcca51a39b11ef8d890b0c6735c41bf73f79bf20a4f6ec288245606aa6
Tx public key: d8b3705dfdf7f34da0fec8b1fdb1f74d4887114c53c4c42e0b439a29cc5a8b59
Timestamp: 1751893997 Timestamp [UCT]: 2025-07-07 13:13:17 Age [y:d:h:m:s]: 00:137:10:49:45
Block: 1320622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96673 RingCT/type: yes/0
Extra: 01d8b3705dfdf7f34da0fec8b1fdb1f74d4887114c53c4c42e0b439a29cc5a8b59021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd616ec0f340dd864bfbd5a6d719e0adfed297ce4144da692746af977a0e51a2 0.600000000000 1808321 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": 1320632, "vin": [ { "gen": { "height": 1320622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd616ec0f340dd864bfbd5a6d719e0adfed297ce4144da692746af977a0e51a2" } } ], "extra": [ 1, 216, 179, 112, 93, 253, 247, 243, 77, 160, 254, 200, 177, 253, 177, 247, 77, 72, 135, 17, 76, 83, 196, 196, 46, 11, 67, 154, 41, 204, 90, 139, 89, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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