Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a84a1698d77bd0730b44b41b85543f205343c74cb8bc5c9c08ff570926fa540

Tx prefix hash: 99814ef94ee7eea9f1a797bf000351c38ea0eec63e24ad85424584be874d361c
Tx public key: 4631fff8850dd071f1e2308ac1ee1d22800a9480801e8e3d36874c84d40aadfd
Timestamp: 1698259105 Timestamp [UCT]: 2023-10-25 18:38:25 Age [y:d:h:m:s]: 01:148:17:24:11
Block: 877523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367293 RingCT/type: yes/0
Extra: 014631fff8850dd071f1e2308ac1ee1d22800a9480801e8e3d36874c84d40aadfd0211000000014b8f5122000000000000000000

1 output(s) for total of 0.759280139000 dcy

stealth address amount amount idx
00: c352de729dfe3bdbe086c18b74bcbe3cb47674e504e9f03fe25e68e8e75fd61c 0.759280139000 1332905 of 0

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": 877533, "vin": [ { "gen": { "height": 877523 } } ], "vout": [ { "amount": 759280139, "target": { "key": "c352de729dfe3bdbe086c18b74bcbe3cb47674e504e9f03fe25e68e8e75fd61c" } } ], "extra": [ 1, 70, 49, 255, 248, 133, 13, 208, 113, 241, 226, 48, 138, 193, 238, 29, 34, 128, 10, 148, 128, 128, 30, 142, 61, 54, 135, 76, 132, 212, 10, 173, 253, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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