Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93e4a3fa7b6306497480264442648dceb2245423f62d8db7c2c9f27053ea830c

Tx prefix hash: 3e1390a1ca36e902ec8c9b0b87f6c225a9b6f5b616827cfc87f9c69fb57ce5bf
Tx public key: 157479e0f0e310ec07867e3649d55f37c66f34875682b1f4a96b8dce5e81c992
Timestamp: 1703427343 Timestamp [UCT]: 2023-12-24 14:15:43 Age [y:d:h:m:s]: 01:321:13:50:23
Block: 920160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488669 RingCT/type: yes/0
Extra: 01157479e0f0e310ec07867e3649d55f37c66f34875682b1f4a96b8dce5e81c99202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41d9fdf57fbd7bbc8c18287ac950d4105abb65aa1bb6906382a6daf1b756eb14 0.600000000000 1377838 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": 920170, "vin": [ { "gen": { "height": 920160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41d9fdf57fbd7bbc8c18287ac950d4105abb65aa1bb6906382a6daf1b756eb14" } } ], "extra": [ 1, 21, 116, 121, 224, 240, 227, 16, 236, 7, 134, 126, 54, 73, 213, 95, 55, 198, 111, 52, 135, 86, 130, 177, 244, 169, 107, 141, 206, 94, 129, 201, 146, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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