Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33560fb82e7356595737dd0d280aa5b56e2a8145271aed6d2640a1a2177b52ef

Tx prefix hash: e75d8c29254d2aeefe0fa924195812124a9ba8f40adb89cdec21549c54540c6e
Tx public key: 7e4739b3647723303822e36d9ce9cfd363c923eb40935716e57fe0c9ebdd802c
Timestamp: 1700236552 Timestamp [UCT]: 2023-11-17 15:55:52 Age [y:d:h:m:s]: 01:188:03:54:49
Block: 893718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395685 RingCT/type: yes/0
Extra: 017e4739b3647723303822e36d9ce9cfd363c923eb40935716e57fe0c9ebdd802c021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.671028952000 dcy

stealth address amount amount idx
00: 082c3ad3e6c5e1e594b56e33e10a2ebdd898d059ec11db71bf171b8d3500a00f 0.671028952000 1349901 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": 893728, "vin": [ { "gen": { "height": 893718 } } ], "vout": [ { "amount": 671028952, "target": { "key": "082c3ad3e6c5e1e594b56e33e10a2ebdd898d059ec11db71bf171b8d3500a00f" } } ], "extra": [ 1, 126, 71, 57, 179, 100, 119, 35, 48, 56, 34, 227, 109, 156, 233, 207, 211, 99, 201, 35, 235, 64, 147, 87, 22, 229, 127, 224, 201, 235, 221, 128, 44, 2, 17, 0, 0, 0, 9, 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