Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63ce44a1e5e1c52ffeb3b7c0a2edccaa776161435f3519364097cf1bad0e2a48

Tx prefix hash: 2202f595db9b53f24dbcd9794c9a30af60accdd4a6c2f58b3b459234f4d95753
Tx public key: e7c369b6828ba1b160cc218ed770e0d82c37b6c854c9c95c33673c610b527ca5
Timestamp: 1703301752 Timestamp [UCT]: 2023-12-23 03:22:32 Age [y:d:h:m:s]: 01:321:18:27:07
Block: 919114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488808 RingCT/type: yes/0
Extra: 01e7c369b6828ba1b160cc218ed770e0d82c37b6c854c9c95c33673c610b527ca50211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68fc635e9e252e09b3b1dc00b6a09128c4a062def04558d804ac96b492d0a1ad 0.600000000000 1376778 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": 919124, "vin": [ { "gen": { "height": 919114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68fc635e9e252e09b3b1dc00b6a09128c4a062def04558d804ac96b492d0a1ad" } } ], "extra": [ 1, 231, 195, 105, 182, 130, 139, 161, 177, 96, 204, 33, 142, 215, 112, 224, 216, 44, 55, 182, 200, 84, 201, 201, 92, 51, 103, 60, 97, 11, 82, 124, 165, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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