Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12ea20b568571e9e02d1f262dc053a8616b8c179046f80e1ec2041e3e94b108f

Tx prefix hash: da21981527527dda1f676424e1ea08089ce09e163e9a94f91e48d95d721531d5
Tx public key: 4cc16ce3744e2bdd0859c82c5e0b02fabf7e97646f5fd044b2c8e041538f50cc
Timestamp: 1728375006 Timestamp [UCT]: 2024-10-08 08:10:06 Age [y:d:h:m:s]: 00:199:18:50:40
Block: 1126990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142584 RingCT/type: yes/0
Extra: 014cc16ce3744e2bdd0859c82c5e0b02fabf7e97646f5fd044b2c8e041538f50cc021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e114124eda1493c97d7c0d59d3138af808ce2751f09f4bec99d7c773dffabddf 0.600000000000 1609789 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": 1127000, "vin": [ { "gen": { "height": 1126990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e114124eda1493c97d7c0d59d3138af808ce2751f09f4bec99d7c773dffabddf" } } ], "extra": [ 1, 76, 193, 108, 227, 116, 78, 43, 221, 8, 89, 200, 44, 94, 11, 2, 250, 191, 126, 151, 100, 111, 95, 208, 68, 178, 200, 224, 65, 83, 143, 80, 204, 2, 17, 0, 0, 0, 5, 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