Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2e98e99f01745461f6ff066a93cff20aecceb519308297b061cf1d6cb546324

Tx prefix hash: 5d75e0a63bb27d0bcca505bf4531f96940d0d5cced0e9aa17f101d8a1c3f9a24
Tx public key: 9c8a259fa4da2f1fd57e480a539bef6081810b79db6f84044f396e439fb8db31
Timestamp: 1634807411 Timestamp [UCT]: 2021-10-21 09:10:11 Age [y:d:h:m:s]: 03:029:14:24:39
Block: 357350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 799380 RingCT/type: yes/0
Extra: 019c8a259fa4da2f1fd57e480a539bef6081810b79db6f84044f396e439fb8db31021100000017f60c5d7e000000000000000000

1 output(s) for total of 40.174596151000 dcy

stealth address amount amount idx
00: d8194d73016e4ee3dbfc2bc43e5b523689e4344dbf530b2f5b22bb824c5c83ac 40.174596151000 728708 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": 357360, "vin": [ { "gen": { "height": 357350 } } ], "vout": [ { "amount": 40174596151, "target": { "key": "d8194d73016e4ee3dbfc2bc43e5b523689e4344dbf530b2f5b22bb824c5c83ac" } } ], "extra": [ 1, 156, 138, 37, 159, 164, 218, 47, 31, 213, 126, 72, 10, 83, 155, 239, 96, 129, 129, 11, 121, 219, 111, 132, 4, 79, 57, 110, 67, 159, 184, 219, 49, 2, 17, 0, 0, 0, 23, 246, 12, 93, 126, 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