Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf2a74a7c6c6d9f599e7e257644925954fa42d340caf800a9cf52e2e5100c76

Tx prefix hash: 577647eda57825f24429e3352a11857f9254b7f97ca38f53a96ba1c3737ba181
Tx public key: e21c801c98241c3f251155ef0e0742246ac982af0ec3f242d87c68671682ae8f
Timestamp: 1750804442 Timestamp [UCT]: 2025-06-24 22:34:02 Age [y:d:h:m:s]: 00:149:05:30:13
Block: 1312107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104585 RingCT/type: yes/0
Extra: 01e21c801c98241c3f251155ef0e0742246ac982af0ec3f242d87c68671682ae8f021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c00ac376f6cbb448c43c53192ecd52d1ab05cf62d35771d00580126d6c4f7ab 0.600000000000 1799738 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": 1312117, "vin": [ { "gen": { "height": 1312107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c00ac376f6cbb448c43c53192ecd52d1ab05cf62d35771d00580126d6c4f7ab" } } ], "extra": [ 1, 226, 28, 128, 28, 152, 36, 28, 63, 37, 17, 85, 239, 14, 7, 66, 36, 106, 201, 130, 175, 14, 195, 242, 66, 216, 124, 104, 103, 22, 130, 174, 143, 2, 17, 0, 0, 0, 2, 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