Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0ed306e41425631f56c90d6c12173c16a672e567ec78bd7e40314467d420141

Tx prefix hash: 56c5b5436d16c1d2e55f761812cca1ba40cbddc3e917536bb229088e27a7621e
Tx public key: 118cdb8f80c78a0af5d4fc29c66570e89c078caf110288fd2fd216ac4792c786
Timestamp: 1723534423 Timestamp [UCT]: 2024-08-13 07:33:43 Age [y:d:h:m:s]: 00:284:20:35:22
Block: 1086860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203506 RingCT/type: yes/0
Extra: 01118cdb8f80c78a0af5d4fc29c66570e89c078caf110288fd2fd216ac4792c786021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0b21a6a7d511e7725ac9da48817e7b9d78efec047f6b610df0f651f860bebbc 0.600000000000 1561459 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": 1086870, "vin": [ { "gen": { "height": 1086860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0b21a6a7d511e7725ac9da48817e7b9d78efec047f6b610df0f651f860bebbc" } } ], "extra": [ 1, 17, 140, 219, 143, 128, 199, 138, 10, 245, 212, 252, 41, 198, 101, 112, 232, 156, 7, 140, 175, 17, 2, 136, 253, 47, 210, 22, 172, 71, 146, 199, 134, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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