Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20203982761c9fd7b09637812c2ceef1164041c10f9d5c3f9ee70ac6cf9315b4

Tx prefix hash: e58d0a19595147e4b9aca1042fd6700ed4218312b9e8f298db16baad9f4a05be
Tx public key: 9495aa9f4c135c3a81dcadd96e0bfc3b47d21f9847f7074f1cc80680b1f48e31
Timestamp: 1731028586 Timestamp [UCT]: 2024-11-08 01:16:26 Age [y:d:h:m:s]: 00:167:10:10:53
Block: 1148901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119504 RingCT/type: yes/0
Extra: 019495aa9f4c135c3a81dcadd96e0bfc3b47d21f9847f7074f1cc80680b1f48e31021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fe76dc4089598df9170ed2c0448cc3c71483c79f4140e639f6ccba4454b3122 0.600000000000 1633862 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": 1148911, "vin": [ { "gen": { "height": 1148901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fe76dc4089598df9170ed2c0448cc3c71483c79f4140e639f6ccba4454b3122" } } ], "extra": [ 1, 148, 149, 170, 159, 76, 19, 92, 58, 129, 220, 173, 217, 110, 11, 252, 59, 71, 210, 31, 152, 71, 247, 7, 79, 28, 200, 6, 128, 177, 244, 142, 49, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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