Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f297d180a7392f90f19c3a813a9ee47216a5f69a45e698fd446cd5065b4970d

Tx prefix hash: dd9ecf76631a30df8f029da4c8b83d0640fa21c189b9daa65bbb0a4573d0fe4a
Tx public key: ed66309cd78eb8c773ec3f57996d0681cdd08611a1a95e7a549e85658fabf751
Timestamp: 1747811226 Timestamp [UCT]: 2025-05-21 07:07:06 Age [y:d:h:m:s]: 00:181:16:09:40
Block: 1287595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127532 RingCT/type: yes/0
Extra: 01ed66309cd78eb8c773ec3f57996d0681cdd08611a1a95e7a549e85658fabf7510211000000071f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ae2c43a00615864947f79a7e92e3e01c8e9fbd4da7255c1a24c0b9c74b05526 0.600000000000 1775062 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": 1287605, "vin": [ { "gen": { "height": 1287595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ae2c43a00615864947f79a7e92e3e01c8e9fbd4da7255c1a24c0b9c74b05526" } } ], "extra": [ 1, 237, 102, 48, 156, 215, 142, 184, 199, 115, 236, 63, 87, 153, 109, 6, 129, 205, 208, 134, 17, 161, 169, 94, 122, 84, 158, 133, 101, 143, 171, 247, 81, 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