Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b18311a7bf06e9239241f37e3f8974447fe7d35c370a8056dbb633d28c954b2

Tx prefix hash: 0556f2e29a0f0c9969bc2b4f7f07fbd62ba49f057c34b54d318cb71131d05a2e
Tx public key: af38f40df0178a7fc507ccdb7d68269751b9422a5abec2f7536da3eddcf5dc71
Timestamp: 1747772336 Timestamp [UCT]: 2025-05-20 20:18:56 Age [y:d:h:m:s]: 00:184:00:04:45
Block: 1287274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129193 RingCT/type: yes/0
Extra: 01af38f40df0178a7fc507ccdb7d68269751b9422a5abec2f7536da3eddcf5dc710211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 027cfb3a694c0d330aa1ffd7fa6dc0cb5e47c7a718912effad492836dfd60fc7 0.600000000000 1774741 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": 1287284, "vin": [ { "gen": { "height": 1287274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "027cfb3a694c0d330aa1ffd7fa6dc0cb5e47c7a718912effad492836dfd60fc7" } } ], "extra": [ 1, 175, 56, 244, 13, 240, 23, 138, 127, 197, 7, 204, 219, 125, 104, 38, 151, 81, 185, 66, 42, 90, 190, 194, 247, 83, 109, 163, 237, 220, 245, 220, 113, 2, 17, 0, 0, 0, 4, 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