Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab6f91c76a7fc4b0f9b95b314287aa63dbb6e7c4a8062450d76147435eb3b2b1

Tx prefix hash: 7b524086f1b366f33214267e594e35ed6ffcb1686931d7fed29c8f33b07fa73f
Tx public key: cf5122c1e854886046fa1c1b894040266e09d8869eb3fa4ad0c8393bbbbf0b85
Timestamp: 1746733221 Timestamp [UCT]: 2025-05-08 19:40:21 Age [y:d:h:m:s]: 00:244:03:08:11
Block: 1278649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172267 RingCT/type: yes/0
Extra: 01cf5122c1e854886046fa1c1b894040266e09d8869eb3fa4ad0c8393bbbbf0b850211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26add60774a46e8b62ae8d7dde516a0a54a79ee93625490f11dba82fb850015d 0.600000000000 1766018 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": 1278659, "vin": [ { "gen": { "height": 1278649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26add60774a46e8b62ae8d7dde516a0a54a79ee93625490f11dba82fb850015d" } } ], "extra": [ 1, 207, 81, 34, 193, 232, 84, 136, 96, 70, 250, 28, 27, 137, 64, 64, 38, 110, 9, 216, 134, 158, 179, 250, 74, 208, 200, 57, 59, 187, 191, 11, 133, 2, 17, 0, 0, 0, 1, 31, 144, 81, 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