Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86edcb456770bb5d276b506ebd11a1e33760c4d6a85283ba541779afff01cb90

Tx prefix hash: d97c28237758fbce5f2005357fec595dd49a1f34744c328ade748b2881ce446d
Tx public key: 3bbb125e9e699ab2775ad7c44db0caa75b1c1392f1f77f2dc14c42f394d2b96d
Timestamp: 1730080485 Timestamp [UCT]: 2024-10-28 01:54:45 Age [y:d:h:m:s]: 00:235:09:48:08
Block: 1141056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167959 RingCT/type: yes/0
Extra: 013bbb125e9e699ab2775ad7c44db0caa75b1c1392f1f77f2dc14c42f394d2b96d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 402eacb610cc48ab583a032a98de1c52e88b7c81fb0713957c3676947fe37ac9 0.600000000000 1624863 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": 1141066, "vin": [ { "gen": { "height": 1141056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "402eacb610cc48ab583a032a98de1c52e88b7c81fb0713957c3676947fe37ac9" } } ], "extra": [ 1, 59, 187, 18, 94, 158, 105, 154, 178, 119, 90, 215, 196, 77, 176, 202, 167, 91, 28, 19, 146, 241, 247, 127, 45, 193, 76, 66, 243, 148, 210, 185, 109, 2, 17, 0, 0, 0, 2, 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