Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f0e5852b43a94c3b618b85f0bcbe1cd329fb35d76a86757c8c534f86ff655b0

Tx prefix hash: 004546d2b1e39eb20dd64e8168eeadcffefbb165c9f137a6f10c07e4b4c86ced
Tx public key: 8e438416aeb8d1c25959afd109d922061c97138d3f31f6f42065479939d15277
Timestamp: 1730019898 Timestamp [UCT]: 2024-10-27 09:04:58 Age [y:d:h:m:s]: 00:157:17:22:53
Block: 1140590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112510 RingCT/type: yes/0
Extra: 018e438416aeb8d1c25959afd109d922061c97138d3f31f6f42065479939d15277021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae99d2ea8ef404444a6760331aa653f92590d3387fb6ddb33efd3abecf67f1b5 0.600000000000 1624391 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": 1140600, "vin": [ { "gen": { "height": 1140590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae99d2ea8ef404444a6760331aa653f92590d3387fb6ddb33efd3abecf67f1b5" } } ], "extra": [ 1, 142, 67, 132, 22, 174, 184, 209, 194, 89, 89, 175, 209, 9, 217, 34, 6, 28, 151, 19, 141, 63, 49, 246, 244, 32, 101, 71, 153, 57, 209, 82, 119, 2, 17, 0, 0, 0, 1, 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