Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f0353e6377319d6bc9ddcc1f92348820b7141c76c579949412330805136236

Tx prefix hash: dd32803f81bb6637c6389e58df94e22f171c1ab5fd55ea7667c50cd6a6b60e02
Tx public key: efb2e02e341fbd6dad88cb23d86626a4ebddb00898a38f82b8c5e91947a4d46c
Timestamp: 1732540543 Timestamp [UCT]: 2024-11-25 13:15:43 Age [y:d:h:m:s]: 00:162:08:05:19
Block: 1161430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115846 RingCT/type: yes/0
Extra: 01efb2e02e341fbd6dad88cb23d86626a4ebddb00898a38f82b8c5e91947a4d46c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c075a89626fdbb21da7c9ebae0209196205cf9e65aaf82944cdb51978ea807d6 0.600000000000 1647085 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": 1161440, "vin": [ { "gen": { "height": 1161430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c075a89626fdbb21da7c9ebae0209196205cf9e65aaf82944cdb51978ea807d6" } } ], "extra": [ 1, 239, 178, 224, 46, 52, 31, 189, 109, 173, 136, 203, 35, 216, 102, 38, 164, 235, 221, 176, 8, 152, 163, 143, 130, 184, 197, 233, 25, 71, 164, 212, 108, 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