Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77c58a886d061841f921307f40f86065e8d2dbba358469aaf247cf8947b3ff0e

Tx prefix hash: 1e44a497d5df7114774d198b504a16a2e6e69bda4999c2b384590e364a0b2c52
Tx public key: 469d57e7d9e7979bec4f9e82343c93477230c3320fb6b82b770ccac70fe7916e
Timestamp: 1732489938 Timestamp [UCT]: 2024-11-24 23:12:18 Age [y:d:h:m:s]: 00:124:14:59:32
Block: 1161005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88874 RingCT/type: yes/0
Extra: 01469d57e7d9e7979bec4f9e82343c93477230c3320fb6b82b770ccac70fe7916e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8eeebfa49cc93dc464b9d93c425b969fedb5b8f8de91f17cb0cf8c61e774645a 0.600000000000 1646656 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": 1161015, "vin": [ { "gen": { "height": 1161005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8eeebfa49cc93dc464b9d93c425b969fedb5b8f8de91f17cb0cf8c61e774645a" } } ], "extra": [ 1, 70, 157, 87, 231, 217, 231, 151, 155, 236, 79, 158, 130, 52, 60, 147, 71, 114, 48, 195, 50, 15, 182, 184, 43, 119, 12, 202, 199, 15, 231, 145, 110, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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