Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ecbce34c4592c083f95d8d8351bec5e3c7080100e0e0a91780e17c58608597f

Tx prefix hash: ae3755190ebd10e93eda3449e722de33ca2e5bf277b4163cf3fc4768e3a37611
Tx public key: d821403c745f1e1faaf8ff57e0a7090e4fca85b3241fe5723f82cabc658ea2ae
Timestamp: 1675761311 Timestamp [UCT]: 2023-02-07 09:15:11 Age [y:d:h:m:s]: 01:274:04:13:53
Block: 691681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456870 RingCT/type: yes/0
Extra: 01d821403c745f1e1faaf8ff57e0a7090e4fca85b3241fe5723f82cabc658ea2ae021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.134538742000 dcy

stealth address amount amount idx
00: b9a0cb866f83087430913d236a07661d4b74f52bc4b6524969d46fa6532e3161 3.134538742000 1134453 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": 691691, "vin": [ { "gen": { "height": 691681 } } ], "vout": [ { "amount": 3134538742, "target": { "key": "b9a0cb866f83087430913d236a07661d4b74f52bc4b6524969d46fa6532e3161" } } ], "extra": [ 1, 216, 33, 64, 60, 116, 95, 30, 31, 170, 248, 255, 87, 224, 167, 9, 14, 79, 202, 133, 179, 36, 31, 229, 114, 63, 130, 202, 188, 101, 142, 162, 174, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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