Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7c2804d61344665fea7fa3c9169a687f4666b3e852fb6dd0fbb4317c95c88bc

Tx prefix hash: c3fb62ba761cdee485624dd5dfb9d3a99394a7365a5c0aedf5ef6cfcbf4c7d87
Tx public key: bb2a22ada115b96ec039bf32cef341faa91f290e912c1564a915e5ff7fd5f16a
Timestamp: 1747527158 Timestamp [UCT]: 2025-05-18 00:12:38 Age [y:d:h:m:s]: 00:143:04:51:06
Block: 1285235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99983 RingCT/type: yes/0
Extra: 01bb2a22ada115b96ec039bf32cef341faa91f290e912c1564a915e5ff7fd5f16a0211000000071f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33411903ab5c60b746387249cd66c95c0f7b9dba761b050cf6803601ea067f21 0.600000000000 1772700 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": 1285245, "vin": [ { "gen": { "height": 1285235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33411903ab5c60b746387249cd66c95c0f7b9dba761b050cf6803601ea067f21" } } ], "extra": [ 1, 187, 42, 34, 173, 161, 21, 185, 110, 192, 57, 191, 50, 206, 243, 65, 250, 169, 31, 41, 14, 145, 44, 21, 100, 169, 21, 229, 255, 127, 213, 241, 106, 2, 17, 0, 0, 0, 7, 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