Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79e8252814fd5983d07c3db5538b3f5eae15035edbb9d9c3c8bf1bb6396f4730

Tx prefix hash: 26fad5ebe0da0f73f8949db050989d4533937a712a96f68b489b25ea25218bd9
Tx public key: 6169ea39911a228803c1f1c4b74bce5f7b598585708be639fc6f52630dd714ad
Timestamp: 1716863405 Timestamp [UCT]: 2024-05-28 02:30:05 Age [y:d:h:m:s]: 01:165:22:14:18
Block: 1031565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377165 RingCT/type: yes/0
Extra: 016169ea39911a228803c1f1c4b74bce5f7b598585708be639fc6f52630dd714ad02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5f579eb381ce670fc3f2ad6fc934b6c1156801dddece604cc98caf477b0b02c 0.600000000000 1500014 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": 1031575, "vin": [ { "gen": { "height": 1031565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5f579eb381ce670fc3f2ad6fc934b6c1156801dddece604cc98caf477b0b02c" } } ], "extra": [ 1, 97, 105, 234, 57, 145, 26, 34, 136, 3, 193, 241, 196, 183, 75, 206, 95, 123, 89, 133, 133, 112, 139, 230, 57, 252, 111, 82, 99, 13, 215, 20, 173, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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