Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fd6f6e7a4e2b9efc88c83a71d753b3718bc4b24d17b1304ea0d44ab4990523d

Tx prefix hash: 683b4037295dbb57a5eb18b1fcd993fbbcd508514a0c554e49b4e8270169790f
Tx public key: f068e79f5144ec56f03ceb4da43086393d749892ddc0b44e21c3db4ae6bbfcc0
Timestamp: 1754823981 Timestamp [UCT]: 2025-08-10 11:06:21 Age [y:d:h:m:s]: 00:007:07:31:12
Block: 1344109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4565 RingCT/type: yes/0
Extra: 01f068e79f5144ec56f03ceb4da43086393d749892ddc0b44e21c3db4ae6bbfcc0021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48ac6ac050cfb5e8ff3e946b30440b29a9797941ea5402b133cb53c938c55a29 0.600000000000 1831980 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": 1344119, "vin": [ { "gen": { "height": 1344109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48ac6ac050cfb5e8ff3e946b30440b29a9797941ea5402b133cb53c938c55a29" } } ], "extra": [ 1, 240, 104, 231, 159, 81, 68, 236, 86, 240, 60, 235, 77, 164, 48, 134, 57, 61, 116, 152, 146, 221, 192, 180, 78, 33, 195, 219, 74, 230, 187, 252, 192, 2, 17, 0, 0, 0, 4, 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