Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 774dd95a903bbf8fb322e2db34ec0d6cd2adb7a6ef20e2df6b60458c4dd1bd50

Tx prefix hash: 1c5b6a4711dcf819cb9bb1d7ec7e556d243089f3130aefd1135f1fad457599e8
Tx public key: 668b9ef39e3bf1e6d95e478cec73b05870b89b2c8c06f4774b39a11fd9c66897
Timestamp: 1739803141 Timestamp [UCT]: 2025-02-17 14:39:01 Age [y:d:h:m:s]: 00:343:00:21:38
Block: 1221269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242837 RingCT/type: yes/0
Extra: 01668b9ef39e3bf1e6d95e478cec73b05870b89b2c8c06f4774b39a11fd9c668970211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6201020c4f7b47eeab8e10b2c669d33b66c28ae4d3284aafbce1f2f4f5257ea2 0.600000000000 1708114 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": 1221279, "vin": [ { "gen": { "height": 1221269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6201020c4f7b47eeab8e10b2c669d33b66c28ae4d3284aafbce1f2f4f5257ea2" } } ], "extra": [ 1, 102, 139, 158, 243, 158, 59, 241, 230, 217, 94, 71, 140, 236, 115, 176, 88, 112, 184, 155, 44, 140, 6, 244, 119, 75, 57, 161, 31, 217, 198, 104, 151, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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