Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2aa82e12a96647084e823a0ce2b0b1f673b658154a0ac506a918cf6a057d7b6

Tx prefix hash: 0e401d5dbcf71ebe425207001a265942ea3243484969a0b73a8f16940dd6eca5
Tx public key: 0a1579f9dd5e59849e1b921e158ae253974f0d35a698a87c25cf009cce7bf09f
Timestamp: 1751515282 Timestamp [UCT]: 2025-07-03 04:01:22 Age [y:d:h:m:s]: 00:213:08:05:18
Block: 1317687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150623 RingCT/type: yes/0
Extra: 010a1579f9dd5e59849e1b921e158ae253974f0d35a698a87c25cf009cce7bf09f021100000021bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d75aa7aefcb3fa7fa597aa00fab1981197ccba62c2b317cb49212be0d121a37 0.600000000000 1805356 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": 1317697, "vin": [ { "gen": { "height": 1317687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d75aa7aefcb3fa7fa597aa00fab1981197ccba62c2b317cb49212be0d121a37" } } ], "extra": [ 1, 10, 21, 121, 249, 221, 94, 89, 132, 158, 27, 146, 30, 21, 138, 226, 83, 151, 79, 13, 53, 166, 152, 168, 124, 37, 207, 0, 156, 206, 123, 240, 159, 2, 17, 0, 0, 0, 33, 191, 81, 178, 162, 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