Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6ee9e56821df8c6470b64491d43f31f1a2dc99c545b274791dd59667b110608

Tx prefix hash: cdc5fe8188eef2e124e5c4376c2e2c8f2e6afd95d4562752ec6ba13e3a73bf4c
Tx public key: c2596ff0db222318c39fdd69476fbc8335c7a2b5929d07c53177aa3ec8cf72bc
Timestamp: 1727391301 Timestamp [UCT]: 2024-09-26 22:55:01 Age [y:d:h:m:s]: 00:149:05:48:48
Block: 1118829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106432 RingCT/type: yes/0
Extra: 01c2596ff0db222318c39fdd69476fbc8335c7a2b5929d07c53177aa3ec8cf72bc02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e2893e7c2ea7b76d9091ccca10d7e020049896157cea8dc846e78c393fcaefd 0.600000000000 1600162 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": 1118839, "vin": [ { "gen": { "height": 1118829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e2893e7c2ea7b76d9091ccca10d7e020049896157cea8dc846e78c393fcaefd" } } ], "extra": [ 1, 194, 89, 111, 240, 219, 34, 35, 24, 195, 159, 221, 105, 71, 111, 188, 131, 53, 199, 162, 181, 146, 157, 7, 197, 49, 119, 170, 62, 200, 207, 114, 188, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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